在優雅的 Ruby 世界中， 基本類型 是邏輯中不可分割的原子。與儲存集合的容器不同，基本類型如 Integer 和 Float 代表單一且精確的值。這些類型繼承自 Numeric 類別，繼承了強大的數學方法基因。
彈性整數
Ruby 以精密的演算法管理記憶體。它區分 Fixnum （位於硬體最佳化範圍內的整數）與 Bignum （任意精度整數）。在 64 位元系統中，界限設定於 $-2^{62}$ 和 $2^{62} - 1$ 之間。
當計算超出這些界限時，Ruby 的內部演算法會執行一次 靜默轉換，並使用可變長度的短整數重新分配記憶體。這能保護開發者免於低階語言中常見的 整數溢出 問題。
與基本類型互動
基本類型並非被動；它們會回應像 .abs 之類的方法，並透過迭代器參與功能流程。為確保嚴格驗證，使用 Integer(object) 方法可確保僅數值相容資料進入您的邏輯，防護系統免受錯誤格式輸入的影響。
main.py
TERMINALbash — 80x24
> Ready. Click "Run" to execute.
>
QUESTION 1
What is the primary difference between Fixnum and Bignum in Ruby's internal architecture?
Fixnums are objects while Bignums are primitive types.
Fixnums occupy a fixed-size hardware-optimized range; Bignums use variable-length memory.
Bignums only store floating-point decimals.
Fixnums are used only for negative numbers.
✅ Correct!
Correct! Ruby transparently switches to Bignum's variable-length representation when an integer grows too large for standard CPU registers.❌ Incorrect
Recall that both are integers, but Bignum is the 'elastic' version used for large values.QUESTION 2
On a 64-bit system, what is the range of a Fixnum scalar?
$-2^{31}$ to $2^{31}-1$
$-2^{62}$ to $2^{62}-1$
$0$ to $2^{64}$
Infinite precision
✅ Correct!
Correct. Ruby reserves some bits for object tagging, leaving 62 bits for the value itself.❌ Incorrect
64-bit systems use the $-2^{62}$ to $2^{62}-1$ range for optimized Fixnums.QUESTION 3
Which method signature would you use for strict conversion of a string into an integer, raising an error if it fails?
string.to_iInteger(object)Numeric.parse(object)object.abs✅ Correct!
Yes! Unlike to_i, which is 'lazy' and returns 0 on failure, Integer() is a strict conversion method.❌ Incorrect
The Integer(object) kernel method is the standard for strict scalar conversion.QUESTION 4
What happens when a result of a math operation shrinks from a Bignum range back into a Fixnum range?
Ruby keeps it as a Bignum to maintain consistency.
The program crashes due to memory fragmentation.
Ruby automatically downcasts the value to a Fixnum.
The developer must manually call
.to_fixnum.✅ Correct!
Perfect. Ruby's memory management is bidirectional and transparent.❌ Incorrect
Ruby manages this automatically without developer intervention.QUESTION 5
[Short Answer] How can we change the first character of each word to uppercase?
Use
str.upcaseApply
str.gsub(/\b\w/) { |l| l.upcase }Use the
abs method on the string.Iterate with
Integer()✅ Correct!
This utilizes a Regex pattern for word boundaries and a block to transform the scalar character data.❌ Incorrect
You need gsub with a pattern like /\b\w/ and a block for transformation.Case Study: The Factorial Memory Expansion
Observing Automatic Scaling in Financial Logic
A financial application calculates compound interest over a century, resulting in values that far exceed standard 64-bit limits. The system must maintain absolute precision without developer-managed memory allocations.
Q
1. Why is Ruby's 'Integer Hierarchy' superior to C++ primitive 'long long' for this specific scenario?
Solution:
In C++, a 'long long' would overflow once it exceeds its fixed bit-width, causing incorrect results. Ruby automatically promotes the value to a Bignum, using a variable-length set of short integers to maintain perfect precision as the number grows.
In C++, a 'long long' would overflow once it exceeds its fixed bit-width, causing incorrect results. Ruby automatically promotes the value to a Bignum, using a variable-length set of short integers to maintain perfect precision as the number grows.
Q
2. If a user provides the input '1_000_000.50' to a method expecting an Integer scalar, how should you handle it to ensure strict numeric integrity?
Solution:
Use the
Use the
Integer('1_000_000.50') method. This will raise an ArgumentError because it contains a decimal, whereas '1_000_000.50'.to_i would silently truncate the value to 1,000,000, potentially losing financial data.